Migrate Legacy Telemetry Custom Ping "crash" to Glean
Categories
(Toolkit :: Telemetry, task, P2)
Tracking
()
People
(Reporter: chutten, Assigned: chutten)
References
(Blocks 2 open bugs)
Details
(Whiteboard: [fog-migration])
The Legacy Telemetry "crash" ping is implemented in the crash reporter client for submission soon after Firefox Desktop crashes or, if that doesn't work out, it is also implemented in toolkit/components/crashes/CrashManager.in.sys.mjs where it is submitted by Firefox Desktop on successful startups after previously-crashed sessions.
A Glean version of this ping was implemented in bug 1790570 (Firefox 111), with the overall "crash" ping Legacy-to-Glean migration meta tracked in bug 1784069.
This bug is about ensuring this ping is Migrated, which for the "crash" ping means:
- Reach out to :gsvelto, Owner of
Core: Crash reporting
, to ensure that the Glean ping introduced over two years ago suits their needs.
Updated•1 month ago
|
Assignee | ||
Comment 1•1 month ago
|
||
Hey, Gabriele, how's the Glean "crash" ping in Firefox Desktop treating you? We're finally at the point in FOG Migration that we're looking at Custom Pings and so we're here to help with any migration-shaped tasks left (if there are any) that'll ensure we'll be in a good state to switch analyses, reporting, and decisionmaking over to the Glean-sent ping before Legacy Telemetry is deprecated and removed in about a year.
You've had this ping for a little over two years, now. Have you noticed it missing something that's in the Legacy one?
Comment 2•1 month ago
|
||
I think we might be almost good to drop the old ping. https://crash-pings.mozilla.org/ is functional (short of a few minor issues here and there) and the dashboards we're using are all based of the Glean pings. Alex, is there something else we still need the lagecy ping for?
Comment 3•1 month ago
|
||
I think we're good to remove the old ping. Let's wait a week or so before doing it: I'll make an announcement that it will be removed, and if there are any stragglers still using it they will hopefully update before forced breakage.
Assignee | ||
Comment 4•1 month ago
|
||
May I recommend this guide we use for communicating data changes? It's helped me in the past.
Oh, and there's no rush on the removal. The only thing needed for this bug's resolution is for the ping to be "Migrated", which for the "crash" ping means "has a Glean equivalent". I'll go ahead and do that now, and leave removal for the ping you mentioned you'd be filing.
Description
•